<html>
<head><meta charset="utf-8"><title>Issues · t-compiler/wg-rustc-dev-guide · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/index.html">t-compiler/wg-rustc-dev-guide</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html">Issues</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="221235675"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221235675" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Iñaki Garay <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221235675">(Dec 30 2020 at 18:47)</a>:</h4>
<p>I went through the RDG issues and grouped them, it's something my brain likes to do to understand the big picture. Sharing it here in case it's of any use to others as well. </p>
<ul>
<li>
<p>OUT OF DATE AND WRONG INFORMATION</p>
<ul>
<li>395 Ambiguous macro call</li>
<li>900 PR follow-up commits strategy at odds with comment from rust-highfive bot</li>
</ul>
</li>
<li>
<p>MISCELLANEOUS</p>
<ul>
<li>474 Lack of <code>README.md</code> in <code>rust</code> repository inner crates.</li>
<li>515 "&gt;" in bash scripts</li>
<li>949 Add logging in rustc itself that links to the dev-guide</li>
</ul>
</li>
<li>
<p>IMPROVEMENTS TO RDG ITSELF</p>
<ul>
<li>64 Writing mentored issues</li>
<li>202 Document compatibility and breakage policies</li>
<li>448 Double-check we did everything from <a href="https://github.com/rust-lang/rust/issues/40902">rust-lang/rust#40902</a></li>
<li>615 The text of the guide should not be included as code comments</li>
<li>619 Collect a set of PRs that help understanding some parts of the compiler</li>
<li>674 Overview Chapter Followup</li>
<li>707 Add "landing pads" to the glossary</li>
<li>708 New Diagrams in the guide</li>
<li>762 Reorganize files</li>
<li>775 Make contributing.md into a series of tutorials</li>
<li>853 Provide "how to use" for each section of rustc-dev-guide</li>
<li>914 Find a way to incorporate the 2D diagram into the section about bootstrapping</li>
<li>924 Add context to "may be out of date" sections</li>
<li>940 Switch from Travis CI to GHA?</li>
<li>948 Add a diagram of how rustc types relate to one another</li>
</ul>
</li>
<li>
<p>MISSING TECHNICAL CONTENT</p>
<ul>
<li>14 "Diagnostics: reporting errors and lints"</li>
<li>81 Parallel rustc</li>
<li>91 Document common manipulations and operations</li>
<li>94 document where various bits of rust are desugared</li>
<li>104 More information on attributes</li>
<li>120 add notes about <code>rustdoc-ui</code> and <code>rustdoc-js</code> tests</li>
<li>123 "Standard library (libstd, liballoc, libcore, libtest) guide"</li>
<li>187 Incremental build on Window</li>
<li>203 Explain all the stable hashing shenanigans</li>
<li>204 document testing for broader set of targets</li>
<li>248 Document how x.py works</li>
<li>295 Incorporate guidance on long error messages</li>
<li>436 document compiler internal environment variables</li>
<li>468 Introduce something about rmeta and metadata in general</li>
<li>552 Document restrictions around <code>#[cfg(bootstrap)]</code></li>
<li>563 Document slice patterns</li>
<li>584 Explain the technical parts of the Walkthrough somewhere</li>
<li>686 Document inline asm</li>
<li>704 Look through closures meeting</li>
<li>726 Add more about why stage 2 is useful and what constraints bootstrapping has</li>
<li>799 Add <code>Compiler::compile()</code> like docs</li>
<li>825 Explaining what is pure function in the context?</li>
<li>892 Update logging for <code>tracing</code></li>
</ul>
</li>
<li>
<p>MISSING TECHNICAL CONTENT: FRONTEND</p>
<ul>
<li>13 the parser</li>
<li>178 document astconv</li>
<li>656 Document AST validation</li>
<li>946 Add a section on the lexer and expand the section on rustc_ast</li>
</ul>
</li>
<li>
<p>MISSING TECHNICAL CONTENT: MIDDLE</p>
<ul>
<li>16 "name resolution"</li>
<li>17 "HIR and HIR Lowering"</li>
<li>174 Guide mentions trait evaluation (as part of selection), but does not explain it</li>
<li>339 Background on <code>impl Trait</code></li>
<li>657 Document Pattern and Exhaustiveness checking</li>
<li>812 rustc-middle shows up in text without explanation</li>
</ul>
</li>
<li>
<p>MISSING TECHNICAL CONTENT: BACKEND</p>
<ul>
<li>331 document MIR-optimizations</li>
<li>442 Introduce something more about Codegen and LLVM</li>
<li>516 Add dump-mir-dir information</li>
<li>517 Add mir-opt-level information</li>
<li>518 Add dump-mir=&lt;val&gt; options</li>
<li>620 Fill in holes in backend chapters</li>
<li>637 improve/fix "codegen" definition</li>
<li>701 Document new mir-opt test format.</li>
<li>770 Fill out MIR section on constants and constant promotion</li>
<li>943 Notes about MIR generation for match expressions</li>
<li>990 On MIR dataflow convergence</li>
</ul>
</li>
<li>
<p>HOW TO DO STUFF</p>
<ul>
<li>71 Switching Out LLVM Backends</li>
<li>87 advice for debugging incremental compilation hashing failures etc</li>
<li>88 Profiling the Compiler</li>
<li>175 Explain how to benchmark the compiler</li>
<li>198 Document IDE Setup</li>
<li>268 Describe how to swap in local modified crate</li>
<li>271 How do I run a single test of libstd with --nocapture ?</li>
<li>285 Provide guidance on working with out-of-tree crates</li>
<li>310 Add information on updating dependencies</li>
<li>443 Explain how to use gdb to debug the compiler</li>
<li>447 Document how to build rustc under the same conditions as in CI</li>
<li>554 Document setup of rust-analyzer specifically for rustc hacking atop "popular" IDE/editors</li>
<li>824 Recommend <code>git absorb</code> in coding conventions section</li>
<li>831 Difficult to find 'How to structure your PR'</li>
<li>850 Add a section on how to use git</li>
<li>866 Document better that it's OK to use CI for testing</li>
<li>873 Document that you don't need to build the compiler to work on libraries</li>
<li>932 Document stabilization PRs for the standard library</li>
<li>942 Document using rustup-toolchain-install-master for working on rustdoc</li>
<li>947 Create examples of using rustc for common tasks</li>
<li>972 Document how to add a new unstable (debugging) flag</li>
<li>991 Document how to set the color for logging output</li>
</ul>
</li>
<li>
<p>LECTURE SERIES</p>
<ul>
<li>356 Transcribe the Compiler Lecture Salsa In More Depth</li>
<li>357 Transcribe the Compiler Lecture RLS 2.0, Salsa, and Name Resolution</li>
<li>358 Transcribe the Compiler Lecture Cranelift</li>
<li>359 Transcribe the Compiler Lecture Rust analyzer guide</li>
<li>360 Transcribe the Compiler Lecture Rust analyzer syntax trees</li>
<li>361 Transcribe the Compiler Lecture rust-analyzer type-checker overview by flodiebold</li>
<li>362 Transcribe the Compiler Lecture oli-obk on miri and constant evaluation</li>
<li>363 Transcribe the Compiler Lecture Polonius-rustc walkthrough</li>
<li>364 Transcribe the Compiler Lecture rustc-chalk integration overview</li>
<li>365 Transcribe the Compiler Lecture Coherence in Chalk by Sunjay Varma - Bay Area Rust Meetup </li>
<li>366 Transcribe the Compiler Lecture How the chalk-engine crate works</li>
<li>367 Transcribe the Compiler Lecture How the chalk-engine crate works 2</li>
<li>368 Transcribe the Compiler Lecture RFC <a href="https://github.com/rust-lang/rust/issues/2229">#2229</a> Disjoint Field Capture plan </li>
<li>369 Transcribe the Compiler Lecture closures and upvar capture</li>
<li>370 Transcribe the Compiler Lecture blitzerr closure upvar tys </li>
<li>371 Transcribe the Compiler Lecture Convert Closure Upvar Representation to Tuples with blitzerr </li>
<li>372 Summarize the Compiler Lecture async-await implementation plans</li>
<li>373 Transcribe the Compiler Lecture async-await region inferencer</li>
<li>374 Transcribe the Compiler Lecture Universes and Lifetimes </li>
<li>376 Transcribe the Compiler Lecture Polonius WG: Initialization and move tracking</li>
</ul>
</li>
</ul>



<a name="221236098"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221236098" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> oliver <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221236098">(Dec 30 2020 at 18:52)</a>:</h4>
<p>what is transcribing?</p>



<a name="221236183"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221236183" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Iñaki Garay <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221236183">(Dec 30 2020 at 18:53)</a>:</h4>
<p>The idea was to watch the lectures and write down the relevant information that was spoken.</p>



<a name="221236196"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221236196" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nagisa <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221236196">(Dec 30 2020 at 18:54)</a>:</h4>
<p>converting speech to text.</p>



<a name="221236314"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221236314" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Iñaki Garay <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221236314">(Dec 30 2020 at 18:55)</a>:</h4>
<p>It's much more work than simply doing that, we had some discussion on whether transcribing, summarizing or another word was more appropriate. I've done some of that and it's harder than what we initially expected, although the information in the videos is there and is certainly worthwhile.</p>



<a name="221236486"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221236486" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> oliver <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221236486">(Dec 30 2020 at 18:57)</a>:</h4>
<p>I thought YT has a transcription service, or there was another<br>
easy one I looked at for a different project where we would be<br>
getting searchable text from meeting recordings, it was trivial</p>



<a name="221236564"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221236564" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Iñaki Garay <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221236564">(Dec 30 2020 at 18:58)</a>:</h4>
<p>I did exactly that, but most work is eliminating speech utterances, deduplicating things said and restarted sentences, and then figuring out how what is said fits in the guide.</p>



<a name="221236659"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221236659" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> oliver <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221236659">(Dec 30 2020 at 18:59)</a>:</h4>
<p>it is useful to be able to do keyword searches over recordings /<br>
meeting proceedings even if output document isn't polished</p>



<a name="221236940"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221236940" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Iñaki Garay <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221236940">(Dec 30 2020 at 19:02)</a>:</h4>
<p>I agree</p>



<a name="221238048"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221238048" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> oliver <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221238048">(Dec 30 2020 at 19:13)</a>:</h4>
<p>it may be something to note on one of the issues<br>
if the content owners wanted to follow that route</p>



<a name="221272596"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221272596" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> pierwill <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221272596">(Dec 31 2020 at 06:16)</a>:</h4>
<p><span class="user-mention silent" data-user-id="209053">Iñaki Garay</span> <a href="#narrow/stream/196385-t-compiler.2Fwg-rustc-dev-guide/topic/Issues/near/221236314">said</a>:</p>
<blockquote>
<p>It's much more work than simply doing that, we had some discussion on whether transcribing, summarizing or another word was more appropriate. I've done some of that and it's harder than what we initially expected, although the information in the videos is there and is certainly worthwhile.</p>
</blockquote>
<p>Maybe "adapting" is the right word?</p>



<a name="221336949"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues/near/221336949" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> oliver <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/Issues.html#221336949">(Jan 01 2021 at 05:36)</a>:</h4>
<p>textual analysis could be done on something very rudimentary<br>
and would be a simple start to presenting the information<br>
if domain experts were expected to step in at some later time<br>
since the ceiling for an adaptation of content could be pretty high</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>